Copy Module Lost Linkset Pairing

Hey,

Just upgraded to v9.5.2.1 and we have a module that is used as a template for others to copy to have all the attributes, views, linkset pairing within a new module after copy. After the upgrade the Linkset Pairing is not being copied when the new module is created, everything else is being copied (attributes, views). Has anyone else seen this or have I found a bug within the v9.5.2.1?

Copying module using Ctrl+C, Ctrl+V to paste

 


jobina - Mon Apr 07 18:33:36 EDT 2014

Re: Copy Module Lost Linkset Pairing
llandale - Tue Apr 08 14:38:20 EDT 2014

Linkset Pairings are not copied.  In fact, they are not even part of the module, they are in fact stored in the module's parent folder.

Re: Copy Module Lost Linkset Pairing
jobina - Tue Apr 08 15:16:20 EDT 2014

llandale - Tue Apr 08 14:38:20 EDT 2014

Linkset Pairings are not copied.  In fact, they are not even part of the module, they are in fact stored in the module's parent folder.

The Linkset pairing definition was copied in the previous version.

Re: Copy Module Lost Linkset Pairing
Mike.Scharnow - Tue Apr 08 17:13:08 EDT 2014

jobina - Tue Apr 08 15:16:20 EDT 2014

The Linkset pairing definition was copied in the previous version.

I can confirm that it works in 9.5.0.0 but not in 9.5.2.0 → yes, you found a bug (or a feature???)...

BR,
Mike

Re: Copy Module Lost Linkset Pairing
llandale - Thu Apr 10 15:11:09 EDT 2014

jobina - Tue Apr 08 15:16:20 EDT 2014

The Linkset pairing definition was copied in the previous version.

It appears I'm behind the times on LinkSet pairings then.

Re: Copy Module Lost Linkset Pairing
BillTidy - Wed May 28 11:19:11 EDT 2014

Stupid question time -> Are you sure you are on 9.5.2.1 and not on 9.5.1.2 ?

We had a very similar issue in 9.5.1.2 that we logged with IBM and it was solved in 9.5.2.1 and that was when dragging a project to a new location, all linkset pairings were deleted from all link modules in the project and also from the module linkset definitions, though the options such as 'only allow' were still in place and all links between objects were still in place.

Because the delete was silent (no errors when dragging+dropping the project) we only discovered the problem when people started trying to create links again in the project.

I just tried both actions again for you (drag+drop to relocate and ctrl-c + ctrl-v to make a copy of a project) and they both work 100% with the 9.5.2.1 client.

Exactly this bug was why we upgraded to 9.5.2.1 to get rid of it.

Re: Copy Module Lost Linkset Pairing
jobina - Wed May 28 17:08:16 EDT 2014

BillTidy - Wed May 28 11:19:11 EDT 2014

Stupid question time -> Are you sure you are on 9.5.2.1 and not on 9.5.1.2 ?

We had a very similar issue in 9.5.1.2 that we logged with IBM and it was solved in 9.5.2.1 and that was when dragging a project to a new location, all linkset pairings were deleted from all link modules in the project and also from the module linkset definitions, though the options such as 'only allow' were still in place and all links between objects were still in place.

Because the delete was silent (no errors when dragging+dropping the project) we only discovered the problem when people started trying to create links again in the project.

I just tried both actions again for you (drag+drop to relocate and ctrl-c + ctrl-v to make a copy of a project) and they both work 100% with the 9.5.2.1 client.

Exactly this bug was why we upgraded to 9.5.2.1 to get rid of it.

Postive that I'm using client and server version 9.5.2.1

Thanks for the response

Im not trying to copy an entire project as you have suggested you have done and it works. I'm only copying a single module within a folder and pasting it to the same location.

Re: Copy Module Lost Linkset Pairing
BillTidy - Mon Jun 02 03:00:55 EDT 2014

jobina - Wed May 28 17:08:16 EDT 2014

Postive that I'm using client and server version 9.5.2.1

Thanks for the response

Im not trying to copy an entire project as you have suggested you have done and it works. I'm only copying a single module within a folder and pasting it to the same location.

I think what you're seeing is that incoming links are not being copied when you copy+paste a single module - this is by design. If you copy+paste a module that has outlinks you should see outgoing links ARE copied. Maybe this behaviour is not what you expect but it is by design (assuming this is the case you are seeing).

Check the DOORS help documentation titled "How copy and move affect links". I copy+paste some of the text here for you...

In-links are only copied if you also copy the module that contains the object at the other end of the link.
Out-links are always copied.
•If the out-link uses a link module that is being copied, the out-link in the copied module uses the copied link module.
•If the out-link uses a link module that is not being copied, the result depends on whether the link module has the same parent project or folder:
◦If the link module has the same parent, a link module with the same name as the original link module is created in the new location. The out-link in the copied module uses the new link module. If a link module with the same name as the original link module exists in the new location, it is used.
◦If the link module has different parent project or folder, it is used for the copied out-link.
External links are always copied because all the information about them is contained in the object.